Conversation
unatasha8
changed the title
|
|
||
| - **Burst limit**: Maximum requests per second (rps), allowing for short traffic spikes. | ||
| - **Sustained limit**: Maximum requests per minute (rpm), ensuring consistent performance over time. | ||
|
|
There was a problem hiding this comment.
Should we split the technical below into another document? It feels odd to get into the "how" when we are explaining the why above.
There was a problem hiding this comment.
I think if we split it, they won't see/read it... the above is 'what' project rate limits are and below is 'how' they need to implement them
Update bucket naming 'threshold' definitions to match new definitions
|
Hey Una, Here's the banner text, along with a proposal for a small restructuring that I think makes the overall navigation cleaner. Proposed structure Three pages:
The key benefit: since New visitors coming via search will also land on the overview first, which means everyone gets context on old vs. new before diving into the details. The banners on the detail pages are then a secondary safety net for anyone who arrives there directly. Banner text for
Banner text for
Both banners: One open item on the parent page: I included a note that customers can check which system applies to them in the Ory Console under Settings → Rate Limits. That's just an idea for now — would actually be quite simple to implement and a nice touch, but it's not there yet. I've marked it as a placeholder so we can either build it or drop the reference before publishing. Let me know if the restructuring works for you! |
…allout to top of files
4 participants
If this pull request addresses a security vulnerability,
I confirm that I got approval (please contact security@ory.com) from the maintainers to push the changes.
Further comments